Fix some links #4733
Merged
Fix some links #4733
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
philrz
commented
Jul 28, 2023
| @@ -1,7 +1,7 @@ | |||
| ## v1.9.0 | |||
| * The [Zed Language Overview docs](docs/language/overview.md) have been split into multiple sections (#4576) | |||
| * Add support for [user-defined operators](docs/language/statements.md#operator-statements) (#4417, #4635, #4646, #4644, #4663, #4674, #4698, #4702, #4716) | |||
| * Add experimental support to the [`get` operator](https://github.com/brimdata/zed/blob/main/docs/language/operators/get.md) for customized methods, headers, and body (#4572) | |||
| * Add experimental support to the [`get` operator](docs/language/operators/get.md) for customized methods, headers, and body (#4572) | |||
There was a problem hiding this comment.
This one was a straight up mistake by me. Normally I'm careful to always use relative links in the CHANGELOG, then when I post these as release notes in GitHub I morph them there to absolute links pointing to the docs site. I just missed this one.
philrz
commented
Jul 28, 2023
| @@ -25,7 +25,7 @@ in `jq`. If there's glaring functional omissions that are limiting your use of | |||
| `zq`, we welcome [contributions](../README.md#contributing). | |||
|
|
|||
| * For the permutations with `ndjson` input the recommended approach for | |||
| [shaping Zeek NDJSON](https://zed.brimdata.io/docs/next/integrations/zeek/shaping-zeek-ndjson) | |||
| [shaping Zeek NDJSON](https://zed.brimdata.io/docs/integrations/zeek/shaping-zeek-ndjson) | |||
There was a problem hiding this comment.
This change was expected. When I made the changes in #4694 I knew the Zeek docs were going to be gone from their prior home on main in the repo, but they weren't yet revealed under any tagged version in the proper docs site, so for the moment I had to point to next. Now we have the tagged v1.9.0 docs, so that means I can drop the next.
mattnibs
approved these changes
Jul 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.